Generally, for most use cases, just having two servers and good backups is the best option. If you have a greenzone, turn your VMs off, do your updates, turn them back on.

Updates essentially never cause issues. Not on hypervisors (at least not on KVM/Xen.) Putting in a lot of complexity, cost, or risk to mitigate a shark attack isn't worth it. You will focus on a false risk.

@Dashrender said in Hyper-V 2019 on a domain:

@PhlipElder said in Hyper-V 2019 on a domain:

All of the above and more but done in PowerShell on our KB site.

New-NetLbfoTeam -Name vSwitch -TeamMembers *

Nice

Thanks

I've posted that before.

@scottalanmiller said in Hyper-V 2019:

@Dashrender said in Hyper-V 2019:

@black3dynamite said in Hyper-V 2019:

It always say evaluation when you need to download Hyper-V.

OK?

Just how it is, they've always labeled it that.

I knew that - I wasn't sure what @black3dynamite intention was?